I'm developing a audiobook application that users can listen books, read them, add them to their fav list and etc. My application size is too heavy, as you guess.
React Native compiles my code while I type, instead pressing cmd +s. So that makes huge frame drops in my mac. Despite my spec is enough for coding. Here is my spec:
MacBook Air
M2, 2022
Chip - Apple M2
Memory - 16 GB
macOS - Ventura 13.0.1
So, my question is: is there anyway tell react native, compile when i press cmd + s
I read some medium and geeksforgeeks article for this issue. But I couldn't find something worth.
Related
My app is ready for release so I need to make the required screenshots for App Store Connect. I use the CN1 simulator to do that.
Today Apple requires 4 screen sizes if the app is for both iPhones and iPads:
iPhone 6.5" 1284 x 2778
iPhone 5.5" 1242 x 2208
iPad Pro 3rd gen 12.9" 2048 x 2732
iPad Pro 2nd gen 12.9" 2048 x 2732
For 3 & 4 the CN1 skin 'iPadPro' can be used (and I can upload identical screenshots if I understand correctly), for 2 the skin 'iPhone8Plus' can be used, but which skin can be used for 1, the iPhone 6.5"?
From help.apple.com:
For iPhone, screenshots for 6.5-inch iPhone Xs Max and 5.5-inch
devices (iPhone 6s Plus, iPhone 7 Plus, iPhone 8 Plus) are required.
These screenshots will scale down for smaller device sizes.
Screenshot specifications:
6.5 inch (iPhone 12 Pro Max, iPhone 11 Pro Max, iPhone 11, iPhone XS Max, iPhone XR), 1284 x 2778 pixels (portrait), Required if app runs
on iPhone.
I don't see any appropriate skins in the CN1 skin download list. Is there one that can be used?
P.S. My app supports 8 languages and let's say I want to show 5 different screenshots, do I really have to provide 8 x 5 x 4 = 160 screenshots? How do other developers deal with this?
I suggest using one of the app screenshot generator companies like these to generate screenshots in the various resolutions for iOS/Android. There are many such companies you can search for, these are a few:
https://theapplaunchpad.com/
https://app-mockup.com/
https://www.appstorescreenshot.com/
https://launchkit.io/
https://play.google.com/store/apps/details?id=cn.gavinliu.snapmod&hl=en_US
This is the best approach as it will always work (even if a new phone comes out tomorrow or requirements change). Notice I'm not affiliated with any of these companies... I did use a few of them for our apps.
Making a skin isn't hard but isn't trivial either. I built a tool a while back that generates skins but it's unmaintained. I find it easier to just add a skin in the project directly here:
https://github.com/codenameone/codenameone-skins/tree/master/Phones/iPhoneX
See the iPhoneX skin. The main challenges here are:
Finding an image of the iPhone where the screen is actually in correct pixel proportions (this is surprisingly hard)
Then generating the images that represent the screen surface areas
Editing the properties file for correct font size, pixel density etc.
Then you can just add it to the bash script in the root/XML build and run the script to generate a skin file. Ideally also submit a PR to the project.
I'm not asking you to do that. I'm just not sure when we'll get around to this bug as there are many issues and tasks in queue and most people pick the first option for appstore submissions (or use physical device screenshots).
I am developing Phonegap Application and my application has scenarios where camera is used very frequently.
In my application I have used custom camera plugin (https://www.npmjs.com/package/cordova-camera-custom) to take picture and use it in my application.
Now when I capture images from this camera 30 times by opening camera and capturing again and again the app goes to crash.
The app just crashes so I am not able to identify the root cause of the crash.
I am not an iOS Programmer though I have tried to check the plugin code but I was not able to find the cause.
You can even check the plugin code on your end if needed.
I have also posted this issue to DevExtreme, the framework which I am using to develop hybrid applications at following link:
https://www.devexpress.com/support/center/Question/Details/T480068
and they found that issue indeed is related to memory shortage. The error message was with bug_type: 298 and fault cause: vm_pageshortage.
Please help me on this, I am struggling on it since long before.
Any Help is greatly appreciated.
My team have been developing Titanium in the past few months, and now we are facing a problem: when we make changes on the View code(change its font, its background or size) , it takes a long time ( about 1 minute ) until we see the result displayed on device. that is really a big waste of time.
I saw the TiShadow already, it's great, but it only support js code( like Alloy.createTableList... ), doesn't support the Alloy XML( I mean you can't see your changes displayed on the screen once change the .xml or .tss file )
I also checked 'forgedUI', but unfortunately it's just an UI design tool, and the bad news is its official website is shut down.
To reduce its compile time, I bought SSD disk for my team. The compile time indeed reduced from 60s to 40s. but it's still too long.
Is there any good tool that could make us debug the titanium faster? or how to reduce Titanium's compile time?
I am able to find following tools which are available for Titanium to reduce the time taken to test the application in device/simulator.
TiShadow : Most widely used and open source.
Rapiddev : Currently only for ios but under rapid development.
LiveView : Available with enterprise version of Titanium.
P.S : With TiShadow I was able to test changes made in tss/views along with controllers. Do monitor the terminal( from where tishadow command is triggered ) to see progress in re-compilation of code.
UPDATED at 2019-04-11: don't use titanium, use React Native or Flutter.
I was wrong.
tishadow allow you to "live view" your Alloy XML/style file when changes.
just use:
$ ti build --platform android --target device --shadow
nothing else to do, you will see your app will launch , and every code you change, your app will reload automatically.
no more "$ tishadow server", no more "$ tishadow apply" ....
really great !
I have developed Windows 8 application. and when I try to run it , to test it on another laptop ; the design got worst and everything appear in bad way.(Fonts, images, ..)
Is that related to the resolution ? If yes How I can solve it ?
How was your app developed? Is this a xaml/cs app or html/js app for windows 8 store apps? Is it in the store yet or only testing? Are multiple resolutions supported?
You'll want to test out various resolutions to see how your app handles them. Two links to test out here with your application:
Windows Store app Development Snack: Simulator tips & tricks
Scaling to different screensre
Another area to check is pixel density. Follow the guidelines for scaling to pixel density to ensure your app looks great when scaled.
I'm building in FlashDevlop as pure AS3.
I'm looking at building a kiosk that uses two screens. Its used to administer tests. So one screen has the test, second the controls for admin the test. I have played with wide app but its not very elegant and I really would like both screens to run full screen on each screen. Is it possible to have one air app spawn two native air windows? A secondary question is it possible to detect multiple screens and target a screen to full screen to? Even something as simple as checking the window size to detect would work, im just not sure I can move and if the low level api will fullscreen on that screen. I could not find any examples of this in the docs.
What docs did you look into? I found it right away.
You'll need the Screen class if you want information on the screens that are connected to the PC. And here's some documentation on using it.
To create new windows, just instantiate a new NativeWindow class and call activate() on it when you're done configuring.
There's a lot of other useful stuff for you in the flash.display package. All the AIR stuff is marked with a little AIR icon. I have to admit that it would have been easier to find if they had put these classes in a separate AIR package.