I have a Question that does the application developed to publish on google web store needs different extensions for Mac and PC ?
If anyone knows the answer and give me some links for the documentation which describes the answer then that would be really helpful.
Thanks
This sounds like a question about how to get started in the Chrome Web Store and perhaps publishing your first extension or app.
The answer to your question is no, you will only need a single format. You upload a single file, a zip file, to your Chrome Web Store Developer Panel and it will be available for both Windows and Mac users for download/installation to their Chrome browsers.
Here is Google's Getting Started Guide: https://developer.chrome.com/extensions/getstarted
Related
I have an app which is a little complicated to figure out details without a help document. I don't want to host the help document only on a web server for users who might not prefer to leave the app and go through the tutorial on a web page. So my question is: Is it possible to make use of DocC tutorial and present the tutorial to my users in the app without leaving the app? Is not, the only solution would be to provide a link for my users to open the web page in Safari I guess. My second question is: Is it possible to host DocC tutorial on an Amazon S3 bucket?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I recently found in news that KaiOS has been used in 4G Volte Enabled feature mobile phones. I was wondering how to create apps for KaiOS. Any help on creating apps for KaiOS has been greatly appreciated.
You can find the kickstart here https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS but as KaiOS is B2G forked i would still suggest you to go to kaiOS official website to check the proper flow for the application development.
Below are the series of steps you need to go through if you don't want to get stuck in between of development:
First you should understand how applications actually work in kaiOS environment and for that you need to first understand the architecture for that. You can give a read to https://developer.kaiostech.com/introduction/architecture for more understanding.
Then comes setup for your application which you will find here at https://developer.kaiostech.com/environment-setup . Mozzila firefox shift+F8 will open the webIDE where you can see your devices connected but for that you should have proper drivers installed for your phone. You can use firefox emulator 2.2 (stable) as well for initial start.
Now its time to have your first application onboard to kaiOS . You can make your application in any of the client specific JS like angular , react or even plain javascript but the important part is to have manifest.webapp in root folder for compatibility.You can give a read to https://developer.kaiostech.com/first-app.
You are able to see your first application on your phone !! Now the real pain arrives when it comes to navigate through the application by keypad but thanks to naviboard library which will do this work for you to align your navigable items and navigate through it by simple API’s. You can find the library at https://github.com/amanboss9/naviboard.
When you are done with navigation part of feature phone, you can go through and develop as much as you can as if it is a web application and can develop a lot of things.
Check the sample project at https://github.com/amanboss9/kaios-angular-app. This Boilerplate can save lot of time when it comes to setting up everything from scratch.It included Angular1.6, naviboardJS(For auto handling navigation part of your application) and Gulp.
KaiOS is based on Mozilla's open source B2G OS. The apps are built purely with HTML/JS/CSS stack and any web application/website that is mobile friendly can be an app with just minor modifications. You can use the inbuilt webIDE to build apps for Mozilla OS, see more here.
https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS/Firefox_OS_app_beginners_tutorial
I used to build apps for Firefox OS before it was dead lets hope to see whether it's reincarnation succeeds.
I will try making apps when I get my hands on the Jio Phone and will update here.
Update:
KaiOS has released a newly updated their website with a new IDE called Kaiosrt which is much better and actually works.
KaiOS is a B2G OS forked from Firefox OS.
You can use Angular/React/Jquery or any JS lib/framework to develop apps on Kaios
Packaged app should have all js/image/html/css file packed locally, External link reference in index.html will not work. Blocked by default- CSP policy.
Mobiles (JioPhone/Nokia Banana phone) with keyboard needs to handle its own key events, Refer Kaios Sample app
This is in the FAQs of KaiOS offical website:
Can I develop apps for KaiOS?
KaiOS is a curated platform for apps and we are working closely with
app developers to provide the best experience for our users. At the
moment we are not accepting submissions into the Store, but will do so
in the future.
(https://www.kaiostech.com/faq/#question-12)
Guess you could leave your contact email there and will get updates in the near future.
KaiOS have officially launched the KaiOS Developer Portal.
It's got everything developers need to start building and distributing KaiOS apps.
Furthermore, build your first app with JavaScript (Vanilla), React,
Vue.js and Angular with code examples herein. Then, testing your
apps with WebIDE or Simulator.
Tools and resources include:
A guide to building your first app, with sample code, reference guides, and software development kits (SDKs).
Instructions for ENV setup to configure your development environment.
A simulator running Gaia and web apps in a Gecko-based environment.
The last two weeks I've been been writing a chrome app in order to update a microcontroller using the chrome.serial API. Now beeing almost ready with the main functionality and trying to publish the application the web store says "The app runs only on Chrome OS".
I'm afraid during development I missed the hint that chrome apps will no longer be supported. Unfortunately I can't easily port it to an extension or progressive web app since the app depends on the chrome.serial.* API
Does somebody know how to publish the app for Windows/Mac/Linux anyhow?
Or maybe how to port to a native app using the chrome.serial api?
Thanks
You can continue using the same Chrome App codebase with NW.js, but you will need to distribute to those platforms another way.
https://nwjs.io/blog/chrome-apps-support/
https://nwjs.io/blog/whats-new-in-0.13/
I noticed that there is software (such as iExplorer) that allows you to access files on an iPhone-device from your Mac.
Now my question is: How can I access iPhone files via Objective-c?
This is only for educational purposes.
I found this: https://github.com/Chronic-Dev/libirecovery but I'm not sure if I'm on the right track.
So it seems that you're looking for an API which makes it possible to access the filesystem of the iPhone from a computer. Well, this API exists, and it's called the MobileDevice framework.
Unfortunately, there's no easy or legal way to access files on your iPhone, especially through Objective-C.
The applications installed on iOS are sandboxed, which means they can only access files in their own directory tree; they have no access/knowledge of other files.
Like you said, you can access files using software like iExplorer, but not programmatically from the iPhone itself.
Here is an old project to browse the iphone. You may be able to get some pointers from it on building an application to do the same with the latest info.
http://code.google.com/p/iphonelist/
Couple that with carbonic acid's post about the Mobile Device Framework and you should be able to do some good stuff.
if I find more unique info ill post it here.
I have an iOS app that uses the Google Docs List API to access and download spreadsheet data. I've done a basic test with upgrading my Google Docs account to Google Drive, and everything still seems to be working okay.
Based on the answer for this question Google Document List API and Google Drive SDK it looks like things will continue to work for awhile.
Are there any steps that mobile devs should be taking now to move to the new API? My main concern is that most of the developer docs so far are related to web apps and not mobile apps so requirements like registering for the chrome web store don't seem to fit. For example:
"Warning: Apps will not have any API access to files unless the app has been installed in Chrome Web Store. To test an app during development, you must first create a listing and install it."
Any guidance or suggestions would be appreciated.
Check this answer for the rationale behind the Chrome Web Store installation: https://stackoverflow.com/a/10476737/186674
Also, we are considering removing the installation requirement for the development and testing phase, we should have some updates soon.
iOS apps using the Documents List API should now update to using the Google Drive API and the newer Google APIs Client Library for Objective-C.
The new API and library are quite a bit easier to use and more efficient than are the older GData alternatives.